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 an issue trying to get a name resolution (GPRS network).
root@GPRSDNS:~# dig +trace mncxxx.mccyyy.gprs
; <<>> DiG 9.7.1-P2 <<>> +trace mncxxx.mccyyy.gprs
;; global options: +cmd
. 6824 IN NS grxns1.xxxxxx.grx.
. 6824 IN NS grxns2.xxxxxx.grx.
;; Received 104 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms
mncxxx.mccyyy.gprs. 86400 IN NS DNS1.mncxxx.mccyyy.gprs.
mncxxx.mccyyy.gprs. 86400 IN NS DNS2.mncxxx.mccyyy.gprs.
;; Received 106 bytes from 191.252.243.12#53(grxns2.xxxxxxx.grx) in 415 ms
;; connection timed out; no servers could be reached
From the "dig +trace" output, looks like the next hop, after 191.252.243.12 cannot be contacted. I guess it's the authoritative name server for the host you're looking up. Could be a firewall problem, or it doesn't allow-queries except from certain hosts, etc
The 2nd dig command gives the correct answer probably because 191.252.243.12 has the record still cached.
So basically the DNS server is ok to response to 191.252.243.12 but not from me ?
If there is firewall (most likely) in between you and the dns server denying access to you and allows access from 191.252.243.12, then yes, it will answer only to that host
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.