Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I can't resolve one domain name : runonce.msn.com. When i use a dig, i have a timeout response and when i use +trace option, i have a result....
# dig runonce.msn.com
; <<>> DiG 9.2.4 <<>> runonce.msn.com
;; global options: printcmd
;; connection timed out; no servers could be reached
# dig runonce.msn.com +trace
; <<>> DiG 9.2.4 <<>> runonce.msn.com +trace
;; global options: printcmd
. 189277 IN NS H.ROOT-SERVERS.NET.
. 189277 IN NS I.ROOT-SERVERS.NET.
. 189277 IN NS J.ROOT-SERVERS.NET.
. 189277 IN NS K.ROOT-SERVERS.NET.
. 189277 IN NS L.ROOT-SERVERS.NET.
. 189277 IN NS M.ROOT-SERVERS.NET.
. 189277 IN NS A.ROOT-SERVERS.NET.
. 189277 IN NS B.ROOT-SERVERS.NET.
. 189277 IN NS C.ROOT-SERVERS.NET.
. 189277 IN NS D.ROOT-SERVERS.NET.
. 189277 IN NS E.ROOT-SERVERS.NET.
. 189277 IN NS F.ROOT-SERVERS.NET.
. 189277 IN NS G.ROOT-SERVERS.NET.
;; Received 360 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 493 bytes from 18.104.22.168#53(H.ROOT-SERVERS.NET) in 108 ms
msn.com. 172800 IN NS ns1.msft.net.
msn.com. 172800 IN NS ns2.msft.net.
msn.com. 172800 IN NS ns3.msft.net.
msn.com. 172800 IN NS ns4.msft.net.
msn.com. 172800 IN NS ns5.msft.net.
;; Received 211 bytes from 22.214.171.124#53(a.gtld-servers.net) in 185 ms
runonce.msn.com. 900 IN CNAME runonce.glbdns.microsoft.com.
;; Received 72 bytes from 126.96.36.199#53(ns1.msft.net) in 172 ms
My nameserver is in Public DMZ. I've desactivate all inspect on my firewall for dns.
;; ANSWER SECTION:
msn.com. 900 IN A 188.8.131.52
;; AUTHORITY SECTION:
msn.com. 113277 IN NS ns1.msft.net.
msn.com. 113277 IN NS ns2.msft.net.
msn.com. 113277 IN NS ns3.msft.net.
msn.com. 113277 IN NS ns4.msft.net.
msn.com. 113277 IN NS ns5.msft.net.
;; ADDITIONAL SECTION:
ns1.msft.net. 120729 IN A 184.108.40.206
ns2.msft.net. 2908 IN A 220.127.116.11
ns3.msft.net. 120729 IN A 18.104.22.168
ns4.msft.net. 120729 IN A 22.214.171.124
ns5.msft.net. 2908 IN A 126.96.36.199
I still cannot understand why you don't get a response using the default udp protocol to query your dns for that particular domain and you get a servfail using tcp.
edns-udp-size defines the size_in_bytes that the server will advertize for an EDNS UDP buffer. Valid values are 512 to 4096, values outside this range will be silently adjusted. The default value is 4096. This statement may be used in a view or global options clause.
Practically it's used to limit the number of packets you receive. Dunno if it helps, but I cannot think of anything else other than you're receining incomplete packets, or the dns sends incomplete packets. There is also the "max-udp-size" that controls the packets you send, but I don't think it works with bind 9.2.4
What you can do is to create a forward zone for the domain msn.com, so any queries for *.msn.com are forwarded to the msn.com authoritative name servers.
About the crc error, I don't know why is happening, but it could be because of the packet you send is truncated somehow. That's why I told you to test edns-udp-size.
Is this destination cisco that appears in the screenshot, a PIX? Maybe this is the culprit.