Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
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...)
Sorry for such a alte reply but I was out last week . 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.
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.
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
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.