Closed mitodeboa closed 2 years ago
Hello @mitodeboa. This is interesting..... it might not be compliant, but I see valid DNS responses for your example outping--.callrail.com
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33667
;; flags: qr rd ra ; qd: 1 an: 8 au: 0 ad: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0; flags: ; udp: 1280
;; QUESTIONS:
;; outping--.callrail.com., type = A, class = IN
;; ANSWERS:
outping--.callrail.com. 60 IN A 35.172.158.224
outping--.callrail.com. 60 IN A 52.201.61.243
outping--.callrail.com. 60 IN A 52.71.57.53
outping--.callrail.com. 60 IN A 3.208.120.77
outping--.callrail.com. 60 IN A 3.220.91.146
outping--.callrail.com. 60 IN A 35.171.220.86
outping--.callrail.com. 60 IN A 54.85.57.206
outping--.callrail.com. 60 IN A 3.94.142.155
;; AUTHORITY RECORDS:
;; ADDITIONAL RECORDS:
;; Message size: 355 bytes
No problems with dnsmasq version 2.87
and the aforementioned domain on my end. Just FYI.
Hello,
I've been using your list for a while now and this past week my dnsmasq was not starting properly due to hostnames containing hyphens and not compliant with various RFCs eg outping--.callrail.com
Greetings