Network guys & gals

azjag

How long do you think it would take to make this happen?

For curiosity sake.

Find more posts tagged with

Save $250 on 2025 certification boot camps from Infosec!

Book now with code EOY2025

Button

Comments

W Stewart

Not really a networking guy but 72 hours to give time for dns propagation.

telnet towel.blinkenlights.nl

Routerronin

W Stewart wrote: »

Not really a networking guy but 72 hours to give time for dns propagation.

telnet towel.blinkenlights.nl

Assuming this is the internets and not some monster lab where it was cooked up.

RouteMyPacket

DNS names, then wait for propogation like stated above..still cool in a nerdy kind of way

petedude

If that isn't classifiable as geek love for Star Wars, I don't know what is.

FloOz

Saw this on Reddit awhile back

DevilWAH

RouteMyPacket wrote: »

DNS names, then wait for propogation like stated above..still cool in a nerdy kind of way

Unless you are running the server that holds the authority for the ip address block. Tracert uses reverse DNS, which is why you see the non standard domain names. Registering a domain or ip block to a Named server of authority is what can take time to propagate. But updated to records to the zone once done will work straight away.

reading about this it was done using a couple of routers and using virtual router forwarding and route policing to get the packet to bounce back and forth. once that's done just adding all the PRT records in DNS to return the correct string in the correct order.

If you do a bit of routing in your job (experienced CCNA or CCNP level) you could do the routing in an hour or two depending how your VRF (virtual routing forwarding) skills are, and then 10-15 min to set up the DNS records assuming you have a DNS server to hand. So may be with planning an evening project.