DNS gone Wrong

[babalwan2000]

I seem to have a dns issue on my domain controller.
I'll explain the setup.
the dc(Win2k3) has 2 Nics. Nic1 is connected to the internet and Nic2 to a wireless basestation which broadcasts dhcp addresses of range(192.168.0.*)
My domain name is registered with No-ip.com here's the problem.

when I do an nslookup on the server e.g

http://www.cnn.com

I get the following
Non-authoritative answer:
Name:

http://www.cnn.com.no-ip.com

Address: 10.10.10.10

Is there a way I can fix my dns. I need a step by step dummies guide of doing this. Iv'e been told to do my reverse and forward lookup zones. I guess this is what has messed it up.
all the help and advice would be greatly appreciated.

 

[GlenJohnson]

Have you tried it from another machine? This is what I get off of my cheapy little laptop running W2K.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-1999 Microsoft Corp.

C:\>nslookup cnn.com
*** Can't find server name for address 192.168.2.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.2.1

Non-authoritative answer:
Name: cnn.com
Addresses: 64.236.16.84, 64.236.16.116, 64.236.24.4, 64.236.24.12
64.236.24.20, 64.236.24.28, 64.236.16.20, 64.236.16.52


C:\>

Click here to learn How to help with tsunami relief...

http://www.google.com/tsunami_relief.html

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.
Don't forget to shop @ theTek-Tips Store

 

[babalwan2000]

Thanks GlenJohnson for your response. Unfortunately this is what I get on another machine:
Quote:
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.0.1: Timed out
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.0.1

> cnn.com
Server: UnKnown
Address: 192.168.0.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

On the second attempt I get the following:
C:\>nslookup cnn.com
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: cnn.com.no-ip.com
Address: 10.10.10.10

Is there away I can troubleshoot my DNS-in form of a step by step guide or tutorial?
Once again thanks for your help

 

[GlenJohnson]

What happens when you ping cnn.com, or run a tracert to cnn.com? Start with basic troubleshooting and see if we can see where it fails. Can you run nslookup on anything, inside or outside the network? Good luck.

Click here to learn How to help with tsunami relief...

http://www.google.com/tsunami_relief.html

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin feel free to join the Tek-Tips in Chicago, Illinois Forum.
Don't forget to shop @ theTek-Tips Store

 

[babalwan2000]

Thanks for your response Glen

I managed to run trace routes to various sites. but when it comes to an nslookup it fails.

I want to know why I keep getting the .no-ip @ the end of the queried URL. and where that IP address of 10.10.10.10 comes from.

thansk once again

 

[Saugilsr]

What you may need to add is a DNS forwarding Address. That is the DNS the server will use when it can't resolve the IP itself. In the DNS window right click the server and go to properties->Forwarders. Also while your there look in the Root hints tab and make sure things are there. Add the IP of your ISP's DNS to the forwarders list.

Also, what is the DNS setting on the network card on the server? It should be set to itself.

The reverse lookup zone will fix the "*** Can't find server" problem. A forward zone resolves Name to IP while a Reverse zone.. well does the reverse IP to name.

http://www.microsoft.com/resources/...proddocs/en-us/sag_DNS_pro_AddReverseZone.asp

So you'll need to add a zone for '0.68.192'.

 

[babalwan2000]

Thanks Saugilsr

This is great as this is were I keep screwing up when I'm trying to create the forward and reverse zones. I've been searching for guides on how to do this, but nothing in detail.

how did you come up with 0.68.192. sorry to be a pain dns config is a total wilderness to me.

 

[Saugilsr]

Its just how reverse zones are setup. Your subnet was 192.168.0.* so the reverse zone is 0.168.192. You won't need to worry about this as windows takes care of it when you set up the zone front-ways. (If thats a word.)
Then DNS will register IP addresses in that zone so that you can resolve IP addresses to computer names.
You computers by default should register themselves in the reverse zone when they regiter in dynamic dns.

 

[ITPangaeaArchitect]

If your domain controller is multihomed...stop it.

You will always have problems. Dopmain Controllers cannot be multihomed and expected to be reliable. A whole slew of issues occur, anything and everything from replicatiom, to authentication for users, authentication for computers, DNS lookup failures, everything.

If you ever call Microsoft, you will not be supported with a multihomed DC.

Do not expect to fix your DNS issues permanently using a multihomed DC, as they will never be fixed permanently.

Here's why.
At startup, the netlogon service tries to register both NICs in DNS, this can be true even if the 2nd NIC is disabled, which is why it must be removed from the server if possible (the likelihood of netlogon registering a disabled NIC is not as high however, as it will use the active as its preferred...normally...but I have seen this happen many times). Anyways, when the netlogon registers these records, there is a 50 50 chance that it will register the wrong NIC, the more NICs, the better chance it will get it wrong...so when this happens, you may have some records that are correct, but others that are wrong...which can cause all of the above symptoms plus some.

Until you fix that, don't even worry about the outside world...as you internal world will end up boned at some point anyways.


For getting to the outside world...use the trusty 4.2.2.2 address as a forwarder, and ensure it is for all DNS domains.

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there

 

[babalwan2000]

Got this working. Simply rebuilt the Domain controller