February 2007 - Test - lists.nanog.org

Re: what the heck do i do now?
by Paul Vixie 06 Feb '07

06 Feb '07

> One thing you might consider is putting together a script to harvest email > addresses from whois records that correspond to the PTR for the querying > IPs. Add to that list abuse, postmaster, webmaster, hostmaster, etc @ the > poorly run domain. Then fire off a message explaining the situation and > that you'll be adding a wildcard record on such and such date (preferably > not 4/1). Script all of this and run it every couple of days until the > date you gave and then follow through with the wildcard entry. This > undoubtedly won't stop all of the whining but you can at least say you > tried. volunteers are welcome to apply for that job. > Perhaps you can get CNet or InfoWorld to pick it and write a story about the > service and the impending change. that, conversely, would be fun. > When it comes right down to it, you've got to do what you've got to do to > recover your domain. You provided a service that many of us relied upon. > The responsibility rests on our shoulders to keep up with the changing > times. 7-8 years is more than enough time for even the laziest of mail > admins to update their config. Think about how much bandwidth has been > wasted over the years with these errant queries... about 1 billionth as much as has been wasted by RFC1918-sourced DNS queries sent to the root name servers OR RFC1918-domained DNS updates sent to AS112. therefore i treat it as a personal annoyance but NOT a waste in its own right.

6 9

TorIX Tours on Tuesday February 6
by Joe Abley 05 Feb '07

05 Feb '07

[Apologies for the following non-operational content; if you are not coming to Toronto next week, hit delete now] For those attending NANOG 39 in Toronto next week who don't already see enough generic data centre space in their normal work week, there will be a TorIX tour on Tuesday February 6, some time after the last BOF/Tutorial finishes. There's a limit to the number of people we can practically haul through building security without causing trouble, so first-come, first-served. If for some bizarre reason there is an unexpectedly large number of people who think touring 151 Front is the right way to spend a Tuesday evening, we might try and do two trips, find people to open more than one suite, etc. If you're interested, sign up here: http://nanog.cluepon.net/index.php/NANOG39TorIXTour Joe

1 1

what the heck do i do now?
by Paul Vixie 05 Feb '07

05 Feb '07

bear with me, this appears to be about DNS but it's actually about e-mail. maps.vix.com has been gone since 1999 or so. mail-abuse.org is the new thing. i've tried just about everything to get traffic toward the old domain name to stop... right now there's a DNAME but it made no real difference. i've taken the maps.vix.com domain away. i've set its NS to "localhost". i've put long TTL's on both good and bad data. the traffic continues. clearly this is my pennance for starting MAPS, and i hear you giggling about it, but i need some advice. once upon a time, someone more insane than myself wanted to close an RBL and did so by replacing it with a wildcard entry. we all hated that since it caused a lot of mail to bounce. (all mail that would otherwise have been received by that RBL's subscribers, in fact.) it did however have the effect of causing the subscribers to reconfigure their mailers to stop querying the now-dead RBL in question. what's the current thinking on this? oh and even though this isn't about bgp i can put some numbers in so that it will seem on-topic. out of 100K DNS queries received by a vix.com nameserver (which is about five minutes worth), here are the toptalkers for maps.vix.com. (and we all know by now that public shaming and notification won't work, i'm not sure why this is relevant, but it looks good, so here it is.) "thoughts?" 2208 68.216.187.10 2156 192.106.1.99 1348 213.239.240.162 1024 192.106.1.100 808 192.106.1.1 742 216.156.2.29 659 216.55.144.5 594 192.203.136.10 592 80.247.227.1 556 24.111.1.180 535 217.18.160.2 523 87.127.246.222 438 192.106.1.9 430 192.203.136.1 384 69.20.2.227 378 213.249.17.10 355 87.98.222.35 353 216.218.185.16 331 213.251.136.18 319 72.41.223.229 274 216.65.0.148 264 61.194.193.9 257 200.75.51.132 251 213.234.128.211 248 213.251.134.167 222 69.38.230.2 208 219.232.224.89 193 213.249.17.11 178 200.75.51.133 175 204.212.38.12 170 209.244.4.235 167 211.5.1.220 158 200.62.191.36 150 195.178.70.10 147 212.125.128.91 147 192.247.72.254 145 202.180.64.9 144 216.46.201.220 135 164.164.149.13 134 203.97.32.3 132 66.98.240.151 129 84.14.44.250 122 206.40.201.230 118 195.14.50.1 108 211.5.1.219 102 64.234.192.7 98 66.235.216.48 88 200.205.163.168 85 69.20.2.243 85 69.20.2.231 85 146.83.183.94 80 202.239.113.18 79 199.60.229.4 79 140.186.4.4 78 68.125.191.131 78 203.97.32.5 72 80.88.192.200 71 192.189.54.17 70 82.210.64.18 69 217.106.235.214 68 202.229.192.20 66 202.154.3.2 64 217.19.24.18 61 213.203.124.146 61 195.96.33.249 57 168.95.1.128 56 203.94.129.130 56 200.69.193.111 56 168.95.1.133 55 72.3.128.125 54 168.95.1.145 53 216.231.41.2 53 210.119.192.6 52 203.141.32.247 52 168.95.1.132 50 80.80.231.223 50 204.145.230.31 49 213.225.90.203 48 61.129.66.75 48 38.115.131.10 47 195.220.32.99 46 64.60.208.40 46 207.12.35.170 46 168.95.1.129 46 168.95.1.126 44 212.42.168.116 44 209.128.208.11 44 168.95.1.148 43 84.14.176.166 43 200.62.191.38 43 154.11.147.2 42 168.95.1.144 41 168.95.1.131 41 168.95.1.127 40 81.240.254.45 40 218.223.31.252 40 209.82.111.202 39 69.20.2.237 39 217.22.50.3 39 211.72.171.75 39 131.188.3.89 38 203.166.97.12 38 199.201.145.162 38 168.95.1.147 38 12.98.160.66 37 69.36.241.228 37 168.95.1.146 37 131.130.199.155 36 200.31.192.18 34 216.174.17.6 34 209.61.163.233 34 200.207.88.142 34 168.95.1.92 32 80.247.228.1 32 69.60.117.147 31 67.18.97.50 30 202.175.151.10 27 168.95.1.99 26 216.127.136.207 26 212.245.255.2 26 195.2.96.2 25 216.244.191.38 25 212.86.129.142 25 199.64.0.252 24 212.55.197.117 24 199.166.210.2 24 154.11.136.2 23 216.65.0.156 23 198.63.210.55 23 194.204.0.1 22 202.134.64.12 21 84.22.6.100 21 211.125.124.33 21 203.198.7.66 21 203.144.168.6 21 203.116.1.94 21 202.96.102.3 21 158.234.250.70 20 65.106.2.117 20 213.191.73.65 19 66.77.137.9 19 64.65.208.6 19 64.122.97.116 19 203.23.72.2 19 194.106.218.42 17 80.255.128.145 17 168.95.192.81 16 194.242.40.3 16 168.95.192.83 15 69.20.2.225 15 210.104.1.13 15 207.7.4.66 15 207.218.192.26 15 207.106.1.2 15 168.95.192.89 15 168.95.192.84 15 140.123.181.1 14 217.10.104.109 14 216.145.96.10 14 212.45.26.98 14 210.238.234.242 14 210.236.36.2 14 193.50.240.2 14 193.225.16.111 14 168.95.192.86 14 150.186.1.1 13 24.96.32.18 13 218.232.110.37 13 213.130.10.10 13 202.237.13.66 13 161.142.201.17 12 168.95.192.80 11 62.252.64.17 11 213.171.195.168 11 211.125.124.34 11 210.253.165.8 11 203.30.161.1 11 202.45.84.68 10 216.127.136.213 10 212.49.128.65 10 203.10.110.104 10 202.134.99.162 10 192.114.65.50 10 168.95.192.88 10 168.95.192.85 ...

31 38

Carrier Hotels/Well Connected locations (Phoenix, AZ)
by Deepak Jain 05 Feb '07

05 Feb '07

Would someone mind forwarding me a list of sites suitable for putting a POP in Phoenix AZ (well connected, lots of fiber carriers, availability of dark/metro fiber, etc, etc.) As a courtesy to the list, private replies please. Thanks in advance, Deepak

1 0

OFFTOPIC - Dell Latitude laptop charger
by Mattias Ahnberg 05 Feb '07

05 Feb '07

My friend Henrik Johansson at Packetfront is attending the Nanog conference but managed to leave home without his DELL Latitude laptop charger. Would someone mind to let him charge his laptop using yours? Reply in private if you can and we'll arrange something. Thanks! -- /ahnberg.

1 1

NANOG 39 BOF: Pushing the FIB limits, perspectives on pressures confronting modern routers.
by Joel Jaeggli 04 Feb '07

04 Feb '07

Just a reminder, This BOF has been scheduled for monday afternoon in the 16:00-17:30 slot in Sheraton hall B/C. If you are going to be at NANOG 39 and you have an interest in the subject or a perspective you'd like to offer please attend the BOF. If you'd like some time set aside on the agenda to share your perspective, mail me and we'll add you, otherwise see you at the microphones! Thanks joelja

1 0

RE: broken DNS proxying at public wireless hotspots
by Lasher, Donn 04 Feb '07

04 Feb '07

>If so, how do you configure your client operating system of choice to use the novel, un-proxied ports instead of using > port 53? * Set up the profile, to your house/work/etc, of your favorite SSH client to forward port 53 local to port 53 on your remote machine. * Make sure your SSH Profile connects to your house/work/etc via IP, not name * make sure there is some sort of DNS server running on the target of your SSH session * make sure your SSH server supports forwarded ports * connect to your house/work/etc. * repoint your local DNS client config to 127.0.0.1 * browse at will * (don't forget to undo this later or risk losing your sanity....) Same type of config works great for HTTP (with squid, and browser proxy settings) etc..

6 7

broken DNS proxying at public wireless hotspots
by Suresh Ramasubramanian 04 Feb '07

04 Feb '07

Right now, I'm on a swisscom eurospot wifi connection at Paris airport, and this - yet again - has a DNS proxy setup so that the first few queries for a host will return some nonsense value like 1.2.3.4, or will return the records for com instead. Some 4 or 5 minutes later, the dns server might actually return the right dns record. ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25634 ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 11 ;; QUESTION SECTION: ;www.kcircle.com. IN A ;; AUTHORITY SECTION: com. 172573 IN NS j.gtld-servers.net. com. 172573 IN NS k.gtld-servers.net. [etc] ;; Query time: 1032 msec ;; SERVER: 192.168.48.1#53(192.168.48.1) ;; WHEN: Sat Feb 3 11:33:07 2007 ;; MSG SIZE rcvd: 433 They're not the first provider I've seen doing this, and the obvious workarounds (setting another NS in resolv.conf, or running a local dns caching resolver) dont work either as all dns traffic is proxied. Sure I could route dns queries out through a ssh tunnel but the latency makes this kind of thing unusable at times. I'm then reduced to hardwiring some critical work server IPs into /etc/hosts What do nanogers usually do when caught in a situation like this? thanks srs -- Suresh Ramasubramanian (ops.lists(a)gmail.com)

7 8

Re: broken DNS proxying at public wireless hotspots
by Peter J. Cherny 04 Feb '07

04 Feb '07

At 04:58 PM 4/2/07, Trent Lloyd <lathiat(a)bur.st> wrote: >> * Set up the profile, to your house/work/etc, of your favorite SSH >> client to forward port 53 local to port 53 on your remote machine. >The flaw here is that DNS operates over 53(UDP), last time I checked >SSH doesn't do UDP port forwarding? At the risk of stating the obvious ... Whats wrong with using an OpenVPN tunnel with appropriate acls ? (It works for me !)

2 1

NPE needed
by Randy Bush 03 Feb '07

03 Feb '07

anyone in toronto area, or arriving sunday morning, can loan us an NPE 400 or G1 or G2 with 512MB? thanks randy

1 0