IPv6 and secondary with stealth primary
Moderator: Moderators
IPv6 and secondary with stealth primary
Hiya, couple of quick questions:
1. Do you have any nameservers with IPv6 addresses? (i.e. accessible via IPv6 rather than just serving AAAA / ip6.arpa PTR records)
2. Is it considered bad form to use a free account for secondary DNS but then stealth the primary?
Thanks.
1. Do you have any nameservers with IPv6 addresses? (i.e. accessible via IPv6 rather than just serving AAAA / ip6.arpa PTR records)
2. Is it considered bad form to use a free account for secondary DNS but then stealth the primary?
Thanks.
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
We do not have any nameservers accessible by IPv6 at this time.
However, if you are interested, we can do so. We are currently announcing 2620:0:950::/48 but haven't routed it internally past our core. Full IPv6 support is on our planning board.
Are you looking for IPv6 support on our Primary or Secondary servers?
However, if you are interested, we can do so. We are currently announcing 2620:0:950::/48 but haven't routed it internally past our core. Full IPv6 support is on our planning board.
Are you looking for IPv6 support on our Primary or Secondary servers?
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
We're currently trying to track down a packet loss issue on the IPv6 connection between us and one of our experimental BGP peers before we deploy it past the core and into the server networks. If we can't resolve the issue, we'll probably disable the session to them and just use the one we have with Sprint.
You should be able to ping/trace to 2620:0:950::242:135 which is several hops inside our network.
You should be able to ping/trace to 2620:0:950::242:135 which is several hops inside our network.
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC
traceroute6 and ping6 from my home box, connected via Goscomb Tech's SixXS tunnel:
Is that the packet loss you speak of? I have a machine that's using he.net, but only tunneled:
Code: Select all
pooh:~ tgarcia$ traceroute6 2620:0:950::242:135
traceroute6 to 2620:0:950::242:135 (2620:0:950::242:135) from 2a01:348:165::217:f2ff:fedb:1437, 30 hops max, 12 byte packets
1 nurse.felin.es 1.046 ms 0.467 ms 0.222 ms
2 gw-204.lon-02.gb.sixxs.net 17.638 ms 19.115 ms 17.457 ms
3 ge-0-0-0-1235.rt0.lon4.ipv6.goscomb.net 19.564 ms 20.586 ms 19.597 ms
4 ae0-30.rt2.lon4.ipv6.goscomb.net 18.038 ms 17.968 ms 18.185 ms
5 2001:7f8:17::1b1b:1 30.96 ms 19.055 ms 18.214 ms
6 10g-2-3.core1.ny4.ipv6.he.net 102.103 ms 89.501 ms 87.429 ms
7 10g-3-1.core1.sjc2.ipv6.he.net 166.496 ms 166.488 ms 171.411 ms
8 10g-1-1.core1.fmt1.ipv6.he.net 169.879 ms 170.836 ms 174.374 ms
9 100m-0-0.tserv2.fmt.ipv6.ipv6.he.net 167.523 ms 167.696 ms 167.638 ms
10 2620:0:950:c0::242:141 192.952 ms 192.928 ms *
11 2620:0:950:c2::242:150 193.399 ms 192.613 ms *
pooh:~ tgarcia$ ping6 2620:0:950::242:135
PING6(56=40+8+8 bytes) 2a01:348:165::217:f2ff:fedb:1437 --> 2620:0:950::242:135
16 bytes from 2620:0:950::242:135, icmp_seq=0 hlim=53 time=192.079 ms
16 bytes from 2620:0:950::242:135, icmp_seq=3 hlim=53 time=197.263 ms
16 bytes from 2620:0:950::242:135, icmp_seq=6 hlim=53 time=190.48 ms
16 bytes from 2620:0:950::242:135, icmp_seq=9 hlim=53 time=191.386 ms
^C
--- 2620:0:950::242:135 ping6 statistics ---
11 packets transmitted, 4 packets received, 63% packet loss
round-trip min/avg/max = 190.480/192.802/197.263 ms
Code: Select all
tgarcia@tom:~$ ping6 2620:0:950::242:135
PING 2620:0:950::242:135(2620:0:950::242:135) 56 data bytes
64 bytes from 2620:0:950::242:135: icmp_seq=1 ttl=58 time=45.7 ms
64 bytes from 2620:0:950::242:135: icmp_seq=5 ttl=58 time=44.9 ms
64 bytes from 2620:0:950::242:135: icmp_seq=8 ttl=58 time=150 ms
64 bytes from 2620:0:950::242:135: icmp_seq=12 ttl=58 time=45.7 ms
64 bytes from 2620:0:950::242:135: icmp_seq=15 ttl=58 time=45.5 ms
64 bytes from 2620:0:950::242:135: icmp_seq=18 ttl=58 time=46.3 ms
--- 2620:0:950::242:135 ping statistics ---
19 packets transmitted, 6 received, 68% packet loss, time 18007ms
rtt min/avg/max/mdev = 44.986/63.128/150.475/39.064 ms
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
Yes, looking healthier. Small loss from my box using he.net (->tiscali->sprintv6):
and just about perfect from Goscomb (->ntt->sprintv6):
Code: Select all
--- 2620:0:950::242:135 ping statistics ---
7922 packets transmitted, 7836 received, 1% packet loss, time 7920924ms
rtt min/avg/max/mdev = 204.014/227.875/4609.261/78.206 ms, pipe 5
Code: Select all
--- 2620:0:950::242:135 ping6 statistics ---
7770 packets transmitted, 7698 packets received, 0% packet loss
round-trip min/avg/max = 179.713/207.299/4737.659 ms
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
Hello, sorry for the delay - I didn't get a reply notification for whatever reason.glendale2x wrote:I've been trying to explain to HE what the problem is, but it seems to have magically gone away as of today. Mind trying it again?
From the box on Goscomb, which is traceroute'ing through HE, running this evening:
Code: Select all
16 bytes from 2620:0:950::242:135, icmp_seq=1866 hlim=52 time=225.107 ms
16 bytes from 2620:0:950::242:135, icmp_seq=1867 hlim=52 time=226.324 ms
16 bytes from 2620:0:950::242:135, icmp_seq=1868 hlim=52 time=224.569 ms
16 bytes from 2620:0:950::242:135, icmp_seq=1869 hlim=52 time=224.468 ms
16 bytes from 2620:0:950::242:135, icmp_seq=1870 hlim=52 time=225.432 ms
16 bytes from 2620:0:950::242:135, icmp_seq=1871 hlim=52 time=225.502 ms
16 bytes from 2620:0:950::242:135, icmp_seq=6893 hlim=53 time=195.055 ms
16 bytes from 2620:0:950::242:135, icmp_seq=6894 hlim=53 time=190.791 ms
16 bytes from 2620:0:950::242:135, icmp_seq=6895 hlim=53 time=194.05 ms
16 bytes from 2620:0:950::242:135, icmp_seq=6896 hlim=53 time=228.716 ms
Goscomb, via HE, same route as post of 23 April:
On HE:
Code: Select all
74045 packets transmitted, 73930 packets received, 0% packet loss
round-trip min/avg/max = 187.926/198.239/1548.788 ms
Code: Select all
74124 packets transmitted, 73942 received, 0% packet loss, time 74122555ms
rtt min/avg/max/mdev = 42.680/52.937/1339.736/56.185 ms, pipe 2
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
We've added AAAA and ip6.arpa PTR records for the core routers and switches. The only impact this has (aside from indicating we're getting ready to roll out some working IPv6 services) is traceroutes into our network should now show DNS names rather than the IPv6 address.
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
-
- Site Admin
- Posts: 598
- Joined: Wed Nov 17, 2004 10:05 pm
- Location: Nevada
- Contact:
IPv6
We will be posting our IPv6 progress at: http://ipv6.rollernet.us/
This site has A and AAAA records and is accessible with IPv6.
This site has A and AAAA records and is accessible with IPv6.
Technical Support support@rollernet.us
Roller Network LLC
Roller Network LLC