Re: one domain not resolving via response-policy zone

2018-01-22 Thread lists
Hey Kai, > If I do a nslookup for one of the otto.de domains I reveive "** server > can't find somehost.ov.otto.de: SERVFAIL" The guideline behind the response-policy is that only an actual response gets rewritten. This is usually an answer from a recursive lookup. If you don't get an answer, th

one domain not resolving via response-policy zone

2018-01-22 Thread Kai Wiechers
Hi List, I setup a response-policy zone to override some Records from external DNS-Servers I can't control. My db.rpz Zonefile: $TTL 4H @   IN  SOA localhost. kai.mydomain.com. (     2018012212  ; serial     5M  ; refres

Re: Domain Not Resolving

2017-11-23 Thread Cathy Almond
On 22/11/2017 14:12, Ron Wingfield wrote: > . . .well, I've received a lot of comment from several people, _most > quite helpful and appreciated_; . . .some rather critical and > condescending.  Regardless, I'll just pursue this resolve while using > other resources .  (BTW, under consideration, "

Re: Domain Not Resolving

2017-11-22 Thread Reindl Harald
Am 22.11.2017 um 15:02 schrieb Ray Bellis: On 21/11/2017 17:30, Reindl Harald wrote: because of https://www.iana.org/help/nameserver-requirements and he should not have allowed this setup at all because "Minimum number of name servers - There must be at least two NS records listed in a delega

Re: Domain Not Resolving

2017-11-22 Thread Ray Bellis
On 21/11/2017 17:30, Reindl Harald wrote: > because of https://www.iana.org/help/nameserver-requirements and he > should not have allowed this setup at all because "Minimum number of > name servers - There must be at least two NS records listed in a > delegation, and the hosts must not resolve to

Re: Domain Not Resolving

2017-11-21 Thread wbrown
Does the lone DNS server even respond on the local network? Do you see DNS traffic flowing to that server? Time for the divide and conquer method of troubleshooting to find where the failure is occurring. Good luck. Confidentiality Notice: This electronic message and any attachments may c

Re: Domain Not Resolving

2017-11-21 Thread Reindl Harald
Am 21.11.2017 um 18:05 schrieb Ron Wingfield: . . .well, I never expected to get "flamed" as by GED, "/As a general observation, not knowing what you're doing is dangerous on the Internet.  Please take some time out of your undoubtedly busy life to try to ensure that you aren't a menace to the

Re: Domain Not Resolving

2017-11-21 Thread Matus UHLAR - fantomas
Am 21.11.2017 um 14:42 schrieb G.W. Haywood via bind-users: The address for localhost (127.0.0.1) should be in /etc/hosts, not in your zone file, and very probably it already is On 21.11.17 15:10, Reindl Harald wrote: that part is not true https://tools.ietf.org/html/rfc1537 says: Note that a

Re: localhost entries in zones, was Re: Domain Not Resolving

2017-11-21 Thread Tony Finch
Reindl Harald wrote: > > interesting - but however "administrators often mistakenly drop the trailing > dot" is nonsense Yeah that's irrelevant, but it doesn't change the conclusion that localhost entries in zones are harmful and unnecessary. Tony. -- f.anthony.n.finchhttp://dotat.at/ - I

Re: localhost entries in zones, was Re: Domain Not Resolving

2017-11-21 Thread Reindl Harald
Am 21.11.2017 um 15:27 schrieb Tony Finch: Reindl Harald wrote: Am 21.11.2017 um 14:42 schrieb G.W. Haywood via bind-users: The address for localhost (127.0.0.1) should be in /etc/hosts, not in your zone file, and very probably it already is that part is not true https://tools.ietf.org/ht

localhost entries in zones, was Re: Domain Not Resolving

2017-11-21 Thread Tony Finch
Reindl Harald wrote: > Am 21.11.2017 um 14:42 schrieb G.W. Haywood via bind-users: > > The address for localhost (127.0.0.1) should be in /etc/hosts, > > not in your zone file, and very probably it already is > > that part is not true > > https://tools.ietf.org/html/rfc1537 says: > Note that all d

Re: Domain Not Resolving

2017-11-21 Thread Reindl Harald
Am 21.11.2017 um 14:42 schrieb G.W. Haywood via bind-users: The address for localhost (127.0.0.1) should be in /etc/hosts, not in your zone file, and very probably it already is that part is not true https://tools.ietf.org/html/rfc1537 says: Note that all domains that contain hosts should ha

Re: Domain Not Resolving

2017-11-21 Thread G.W. Haywood via bind-users
Hi there, On Tue, 21 Nov 2017, Ron Wingfield wrote: ... our registered domain, archaxis.net, is not resolving ... As has been mentioned, you don't have a nameserver listening on IP 162.202.233.81. At a guess, you need to restart it. We run BIND version 9.10.2 ... Upgrade. See for exampl

Re: Domain Not Resolving

2017-11-20 Thread Reindl Harald
Am 21.11.2017 um 00:02 schrieb Mark Andrews: And the point of require multiple nameservers is to provide redundancy. There is no redundancy when both servers have the same address. https://www.iana.org/help/nameserver-requirements Network diversity The name servers must be in at least two

Re: Domain Not Resolving

2017-11-20 Thread Mark Andrews
And the point of require multiple nameservers is to provide redundancy. There is no redundancy when both servers have the same address. [rock:~/git/tld-report] marka% ping 162.202.233.81 PING 162.202.233.81 (162.202.233.81): 56 data bytes 64 bytes from 162.202.233.81: icmp_seq=0 ttl=45 time=520.

Re: Domain Not Resolving

2017-11-20 Thread Tony Finch
Ron Wingfield wrote: > ns1 IN A 162.202.233.81 > ns2 IN A 162.202.233.81 This address isn't responding to DNS queries. Tony. -- f.anthony.n.finchhttp://dotat.at/ - I xn--zr8h punycode Sole, Lundy, Fastnet, Irish Sea: S

Domain Not Resolving

2017-11-20 Thread Ron Wingfield
Resolution of our registered domain, archaxis.net, is not resolving . . .cannot be found. This has worked for past months until 3 NOV 2017, when it started failing. Additionally, the email server, Sendmail, has stopped receiving email, and cannot send mail to a DNS-aware MTA such as sbcglobal.net