I would say route advertisements for the failing addresses are not making it
the point in the network where traceroute fails.
At this point you need to see if you can find a looking glass for that net to
check the BGP route announcements for the failing addresses and possibly
escalate to that n
I don't disagree with what you say about nameserver diversity but don't feel
that is the issue here and is missing the point in my question.
I'd already eliminated "lookup" of the DNS servers by going straight to the IP
they share.
Connections from locations outside our network to that IP port
Am 05.12.2017 um 20:21 schrieb Barry S. Finkel:
The problem is not with the "two" name servers for the domain
you are trying to reach. Note the quotation marks.
I was able to contact the ONE IP address and get a DNS
response. If, for some reason, you do not have a path
to that IP address, you
On 12/5/2017 "Lightner, Jeffrey" wrote:
We're having issues send email to a user @SIDDHAFLOWERS.COM
Investigation here shows that the issue we have is querying your name servers
(both by name and by IP) are refusing to respond to our name servers.
Their name servers:
NS1.QUICKFIX8.COM
NS2.QUI
DNS, by design, is generally speaking agnostic when it comes to providing
answers to DNS questions. It would have to be a very deliberate edit to the
"allow-query" option in the conf file to enable your construct of a "DNS
blacklist". In an enterprise environment this type of defensive action
Hi Jeffrey,
I had same kind problems with my domain "smallfusion.net". It's
resolving at few places, mostly it's saying connection timed out; no
servers could be reached.
Well it's very strange.
I'm using Cloudflare.com services with this domain.
___
Pl
We're having issues send email to a user @SIDDHAFLOWERS.COM
Investigation here shows that the issue we have is querying your name servers
(both by name and by IP) are refusing to respond to our name servers.
Their name servers:
NS1.QUICKFIX8.COM
NS2.QUICKFIX8.COM
Our name servers:
DSWADNS1.WATE
7 matches
Mail list logo