Advertisement

Powered by Squarespace
Popular Categories
Blog Posts
Discussion Activity
Cisco Live 365

home

[SYN] [SYN-ACK] [ACK]General Network Error! Check your network documentation.

generalnetworkerror.com is dedicated to dispelling the myth that the network is usually the source of unknown and errant behavior in applications. This is rarely the case in a well-designed network.  The difference of application to network errors is usually orders of magnitude, and geometrically increases with load. 

We will explore various networking topics from real-world experiences, ranging from L2-L3 configuration and troubleshooting to L5/L7 load-balancing to the infamous general network error.  Although many possibilities exist to accomplish a given task, tried and true methods will be presented, but these should only be taken under consideration for use in your own network after proper vetting for fit and function.

Please check out one of the most recent blog entries. You may find what you’re seeking quicker by using the Search box or jumping into the Blog posts or Forums.

 

Google .PROD gTLD rears its head and screams “look at me”

Google’s DNS registration of .PROD through its Charleston Road Registry has caused some name resolution issues internally when using non fully qualified domain names (non-FQDNs).  For those of us who have DNS search suffix lists that attempt to resolve shorter names in a PROD domain by appending an example.com suffix to yield .prod.example.com, you may see now unexpected answers in DNS.

Any names being resolved that end in “.prod” with “example.com” in your search list no longer works.  Since .prod is now a valid gTLD (generic top-level domain), DNS is attempting to resolve this through Google’s registry.  Google, in their infinite wisdom, is returning valid responses instead of negative answers as intended by the RFCs

Read More