Problems with DNS
Howzit
I have M$ nameserver running which resolves all my M$ requests but with my Linux Box itś a no go. Under /etc/resolv.conf file I have placed the Ip for the servers and still no go. What am I doing wrong. chow |
Can you paste the contents of your /etc/resolv.conf here please?
Your entries should look like: nameserver 1.2.3.4 nameserver 1.2.3.5 |
Howzit
Yip that's how it's been setup nameserver xxx.xxx.xxx.xxx nameserver bbb.bbb.bbb.bbb when I ping it gets a response that says: unkown host chow |
Sorry i should have asked this before, but If you put another known working DNS server in your resolv.conf file like your ISP's will it work...Thereby isolating it to specifically having a problem with the windows DNS server. Also Is this the IIS DNS server and what version of windows please. Thanks.
|
Howzit
This is a W2k server running in the internal part of our network the other DNS server is a linux box and is setup just to resolv addr from the outside. chow |
Bom dia, ;-)
Is there any firewall in the way of that box and the dns server you're trying to reach? Can you ping the nameserver from your linux box using its ip instead of its name? (i assume, judging from the answer you gave about pinging it, you did it using the hostname before...) Xau |
Howzit
Sorry for such a alte reply but I was out last week :p. Yes to the quetion if I am able to ping the DNS server with IP, the FW is also not enabled.......... I also added thge following line to the /etc/resolv.conf file to see if anything happend. search mydomain.pt nameserver xxx.xxx.xxx.xxx nameserver bbb.bbb.bbb.bbb I tried pinging the server coflx01 & coflx01.mydomain.pt and nothing Thanx for the responses so far chow |
A better way to test would be by using dig.
dig @ip-of-ms-ns google.com dig @ip-of-ms-ns some-internal-host etc... if you have your Linux box name server setup as authoritative for your zone, but you are in fact looking for hosts in your zone that are only defined in internal DNS, then you're getting exactly what you asked for. Your Linux box won't resolve it because it's not in the external version of your DNS zone. That's why you need to dig specifically off the internal server to see what answer you get. By the way it's entirely possible that there is a firewall between your Linux box and the MS box, one that you do not control. Check with your network/security team to see if there is a firewall between the Linux box and the MS box. If so, they will need to allow the Linux box to make requests on port 53/TCP&UDP to the Windows box. |
Howzit
when i dig @my.domain.pt coflx01 which is a internal machine it says canīt find my.domain.pt but if I do a dig -x xxx.xxx.xxx.xxx coflx01 it responsded and resolves it. The answer to the FW quetion is no thereis no FW between me and the W2K box as I am the network admin :rolleyes: ;) just wondering why this never worked chow |
Can you ping anything on the internet like 4.2.2.2 (it's a DNS server somewhere, i just remember the IP because it's easy)
if you cant ping anything at all then the problem is beyond DNS. check also for a firewall on the linux box. iptables -L iptables -L -t nat |
Howzit
can ping everthing thats un IP but not a name I have disabled FW buy service iptables stop then service iptables save. chow |
You have your dig backwards. To the immediate right of @ should be your name server. The record you're looking for can either come directly to the left of the @ (google.com@ns1.google.com) or after the name server with a space (@ns1.google.com google.com).
Assuming the IP of your Windows nameserver is 192.168.2.2 you can look for a host in internal DNS like this: dig @192.168.2.2 coflx01.domain.pt, this should locate the A record for coflx01 in the internal DNS zone. |
Howzit
Thanx everyone for your help and quick responses I have just worked it out that the domain name in my resolv.conf file was incorrect changed that and :D Once again Thanx chow |
All times are GMT -5. The time now is 03:47 PM. |