Hi everyone,

although not a newbie have to admit DNS not being my strong point so bear
with me...

Got 2 Advanced servers first running primary DNS and the second backup DNS.
Their IP addresses are 192.168.1.1 and 192.168.1.3. All the machines on the
LAN point to them and they point to themselves (in TCP/IP settings). I have
setup 2 forwarders pointing to the ISP's DNS and all browsing seems to work
well. When it comes to emails though it is a different story as it all goes
pearshaped and I am almost 99% sure it is the DNS's fault.

Almost all mail gets bounced back. I have an Exchange 2000 server and the
ISP points the MX records down to the public IP address of the Exchange so I
do not have any MX records configured in my DNS. The AD name is a dummy
street.domain.co.uk and my domain is domain.co.uk. I also keep email for
domain2.co.uk and domain3.uk.com.

When I NSLOOKUP I get the following:

Default server: servername.street.domain.co.uk
Address: 192.168.1.1

If I need to resolve a name (I think here lies the problem) for example
www.google.com I get:

Server 192.168.1.1
Non-authoritative answer
Name: www.google.com.domain.co.uk
Address: xxx.xxx.xxx.xxx (<-- this address is public but it does not belong
to me (or my ISP) it looks like an old forwarder for one of the MX records
of one my domains...)

Thanks in advance!

Kou

Still cannot explain this though...

Server 192.168.1.1
> > Non-authoritative answer
> > Name: www.google.com.domain.co.uk





"Arxitektwn" <(E-Mail Removed)> wrote in message
news:bgmk16$kfs$(E-Mail Removed)...
> Thanks Lanwench,
>
> the made 5 recipient policies: default (*) for the dummy address, and then
> filtering by groups of people for the other 5 domains... Should everything
> fall under the same default policy or did I do it correctly?
>
> After doing a traceroute to my exchange box I found it ending by a public
IP
> that is not mine... Who could have done this?
>
> Many thanks,
>
> Kou
>
>
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed)> wrote in
message
> news:#lewL#(E-Mail Removed)...
> > Check out your domain at www.dnsreport.com - much nicer than nslookup
for
> > most purposes.
> > Also, make sure your recipient policy is set up properly, all mailboxes
> are
> > stamped with the right e-mail addy, and that port 25 is open in your
> > firewall and forwarded to your Exchange server's LAN IP.
> >
> >
> > Arxitektwn wrote:
> > > Hi everyone,
> > >
> > > although not a newbie have to admit DNS not being my strong point so
> > > bear with me...
> > >
> > > Got 2 Advanced servers first running primary DNS and the second
> > > backup DNS. Their IP addresses are 192.168.1.1 and 192.168.1.3. All
> > > the machines on the LAN point to them and they point to themselves
> > > (in TCP/IP settings). I have setup 2 forwarders pointing to the ISP's
> > > DNS and all browsing seems to work well. When it comes to emails
> > > though it is a different story as it all goes pearshaped and I am
> > > almost 99% sure it is the DNS's fault.
> > >
> > > Almost all mail gets bounced back. I have an Exchange 2000 server and
> > > the ISP points the MX records down to the public IP address of the
> > > Exchange so I do not have any MX records configured in my DNS. The AD
> > > name is a dummy street.domain.co.uk and my domain is domain.co.uk. I
> > > also keep email for domain2.co.uk and domain3.uk.com.
> > >
> > > When I NSLOOKUP I get the following:
> > >
> > > Default server: servername.street.domain.co.uk
> > > Address: 192.168.1.1
> > >
> > > If I need to resolve a name (I think here lies the problem) for
> > > example www.google.com I get:
> > >
> > > Server 192.168.1.1
> > > Non-authoritative answer
> > > Name: www.google.com.domain.co.uk
> > > Address: xxx.xxx.xxx.xxx (<-- this address is public but it does not
> > > belong to me (or my ISP) it looks like an old forwarder for one of
> > > the MX records of one my domains...)
> > >
> > > Thanks in advance!
> > >
> > > Kou
> >
> >
>
>

In news:bgmk16$kfs$(E-Mail Removed),
Arxitektwn <(E-Mail Removed)>, posted their thoughts, then I offered my
thoughts down below:
> Thanks Lanwench,
>
> the made 5 recipient policies: default (*) for the dummy address, and
> then filtering by groups of people for the other 5 domains... Should
> everything fall under the same default policy or did I do it
> correctly?
>
> After doing a traceroute to my exchange box I found it ending by a
> public IP that is not mine... Who could have done this?
>
> Many thanks,
>
> Kou
>

Who are the DNS server authorative for those domains? Your ISP? If so, ask
them to straighten it out.

You can check your domain name at the registrar you registered it at to
determine who the authorative servers are and that they are the ones you
specified when purchasing the domains.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

In news:bgmnqv$qih$(E-Mail Removed),
Arxitektwn <(E-Mail Removed)>, posted their thoughts, then I offered my
thoughts down below:
> Still cannot explain this though...
>
> Server 192.168.1.1
>>> Non-authoritative answer
>>> Name: www.google.com.domain.co.uk
>
>


Non authorative means that the zone doesn't exist on that machine and had to
go elsewhere to find it.

If a zone exists on a DNS server, then it's "authorative" for that zone.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

A> Almost all mail gets bounced back. [...]

How do you know that this is because of a DNS problem ?
What are the actual error messages ?

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/problem-report-standard-litany.html>

A> When I NSLOOKUP

Use a good DNS debugging tool. "nslookup" is a bad one.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-daft-error-message.html>

Ironically, you're being confused by one of the
idiosyncracies of "nslookup".

A> Name: www.google.com.domain.co.uk

Give fully qualified domain names to your DNS debugging tool.

<URL:http://www.menandmice.com/online_docs_and_faq/glossary/fqdn.htm>