Re: TFTP over anycast

2024-02-22 Thread Thomas Mieslinger
I do NTP, DHCP, TFTP, DNS, HTTP anycast. NTP, DNS and HTTP with ECMP, TFTP and DHCP as active/active on a per Datacenter Basis. These are small Datacenters with less than 50k Servers each. In every datacenter an anycast node is active and the router just chooses the shortest path. It becomes

ns1-proddns.glbdns.o365filtering.com unreachable?

2022-07-06 Thread Thomas Mieslinger
Anyone else with trouble to reach the *.o365filtering.com DNS Servers?

Re: NXDOMAIN Resolvers

2022-04-21 Thread Thomas Mieslinger
There are public and commercial offerings for "DNS based protection". e.g. 9.9.9.9 automatically generates NXDomains for suspected malicious DNS Names even in their free service. They have a page where you can check if you have been blacklisted (see https://www.quad9.net/de/result) On 4/20/22

Re: IP tracking system

2021-12-16 Thread Thomas Mieslinger
Am 15.12.21 um 19:22 schrieb Rich Greenwood via NANOG: On Wed, Dec 15, 2021 at 4:00 AM mailto:nanog-requ...@nanog.org>> wrote: From: Mauricio Rodriguez mailto:mrodrig...@fletnet.com>> This one seems to be popular and complete: https://phpipam.net/ . We use

anyone from cisco.com DNS Team around?

2020-12-09 Thread Thomas Mieslinger
Hi, I have trouble to activate my Cisco NCS5xxx Devices. Turns out that tools.cisco.com. resolves to either 173.37.145.8 (this works) or 72.163.4.38 (which was decommissioned earlier this year). By running dig A tools.cisco.com @alln01-ucs-dcz03n-gslb1-snip.cisco.com four times I can

Re: a quick survey about LLDP and similar

2019-03-04 Thread Thomas Mieslinger
A little more on the "it depends" switches connected to end-user/customer gear: never ever. switch to switch, switch to router interfaces: yes, to validate cabling and resolve problems as quickly as possible. switch to server interfaces: only to servers of teams you can trust. temporarily

someone from easydns here? dns3.easydns.org. 2620:49:3::10 unreachable from AS8560 and 6939

2017-11-07 Thread Thomas Mieslinger
Hi, can someone operating easydns nameserver check whether 2620:49:3::10 is answering? I create a atlas measurement https://atlas.ripe.net/measurements/10137819 and I can see that some AS still can reach 2620:49:3::10 but many many timeouts. For me, it stops working after 2a00:dd80:9:3::2