I have 3 content switches acting as DNS servers for my website. Occasionally they respond to valid A record queries with an rcode 3 name error. The problem is that this error is cached by some internet DNS servers and clients cannot resolve an address for my website until the SOA expires and there is a successfull refresh. Oddly enough this only seems to occurr with requests/queries from Verizon and Level 3. Queries via DNSStuff.com are always successfull. I'm running version 08.10.1.06.
Yes, that is the way they are set up. The CSS(s) are responsible for replying with the "A" record if the backend service is up. The problem is, if someone reboots the server and there is a request during that time, the CSS returns an error/Rcode of 3. These return codes are cached by some name servers on the internet. The result is, that after the server is back online it is still unresolveable by some clients due to the name server cacheing the record. The web server is unresolvable until the TTL expires in the SOA record.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...