In message <41289c2b-b161-4dda-bdf3-f4c60ec2e...@dataix.net>, Jason Hellenthal
writes:
> Hey thanks for replying Doug.
>
> Sorry for the top post.. iPhone.
>
> Anyway yes these are private or internal zones.
>
> Software is more so the root cause but attempts to resolve to
> hostname.tld from a d
Hey thanks for replying Doug.
Sorry for the top post.. iPhone.
Anyway yes these are private or internal zones.
Software is more so the root cause but attempts to resolve to hostname.tld from
a device that's managed from domain.tld where you'd expect to see it asking for
hostname.domain.tld ins
Jason,
What you're saying here doesn't make sense, so some more details are
needed.
On 06/11/2013 08:54 PM, Jason Hellenthal wrote:
I have a domain or two that I'm serving up and have traffic from some
mobile devices and a few pieces of software that also try to resolve to
the hostname.tld i
Clue bat needed... :-)
Poised with a deception of documentation hello list members.
Curious if someone has faced the following.
I have a domain or two that I'm serving up and have traffic from some mobile
devices and a few pieces of software that also try to resolve to the
hostname.tld instead
On Jun 11, 2013, at 4:12 PM, Gary Wallis wrote:
> DNS experts:
>
> What really happens in the real world when 1 out of three authoritative NSs
> are down for 30 minutes due to a datacenter outage?
Properly functioning nameservers will note that queries sent to the NS which is
down aren't getti
DNS experts:
What really happens in the real world when 1 out of three authoritative
NSs are down for 30 minutes due to a datacenter outage?
For example, we have 3 NSs:
ns1.someisp.net 12.23.34.45
ns2.someisp.net 23.34.45.56
ns3.someisp.net 34.45.56.67
All in different datacenters.
All are a
6 matches
Mail list logo