On 07/08/2014 06:03, Jared Empson wrote:
What our cache server receives:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38342
;; flags: qr ; QUESTION: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1280
;; QUESTION SECTION:
;losscontrol360.com [2]. IN A
;; ANSWER SECTION:
losscontrol360.com [2]. 173 IN A 74.208.98.80
What Google provides: ; <<>> DiG 9.8.3-P1 <<>> losscontrol360.com [2]
@8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17193
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;losscontrol360.com [2]. IN A
;; ANSWER SECTION:
losscontrol360.com [2]. 586 IN A 74.208.98.80
;; Query time: 174 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Aug 6 16:01:07 2014
;; MSG SIZE rcvd: 52
Apart from stupid SOA values, losscontrol360.com seems OK, and from your
two examples here even proves that, if your customers don't see what
your cache server does, they cant be using the same cache server as you
showed here. what error does bind log when your customer looks it up?
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
