Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: possible dns issue

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Nov 2008
    Posts
    15

    Default possible dns issue

    just read this at dslreports

    internet users face the risk of losing their internet connections on 5 May when the domain name system switches over to a new, more secure protocol.

    While the vast majority of users are expected to endure the transition to DNSSEC smoothly, users behind badly designed or poorly configured firewalls, or those subscribing to dodgy ISPs could find themselves effectively disconnected...."

    »www.theregister.co.uk/2010/04/13/dnssec/
    -------------------------------------------------------------------------

    tested 156.154.70.1 and 156.154.71.1 (both used by voipo in phone adapter) and the site is not ready for May 5 change. Public dns servers that I use (4.2.2.2., 4.2.2.3, 4.2.2.4) all show ready.

    Does this mean the service will be affected if the site does not get ready by then?
    dvijen

  2. #2
    Join Date
    Feb 2010
    Posts
    221

    Default Re: possible dns issue

    Those IP addresses you show are those your ISP provides - the adapter is just using DHCP. I use OpenDNS and it "fails" the test too, but the OpenDNS people say that things will still work after the 5th.
    Steve

  3. #3
    Join Date
    Dec 2009
    Location
    MA
    Posts
    166

    Default Re: possible dns issue

    Quote Originally Posted by holmes4 View Post
    Those IP addresses you show are those your ISP provides - the adapter is just using DHCP.
    Those IP addresses are those coded in the ATA device by VOIPo. I have my VOIPo device (PAP2T) behind a WRT54GL (running Tomato). Comcast provides the WRT54GL DNS servers of 68.87.71.230 and 68.87.73.246. The PAP2T shows 156.154.70.1 for Primary, and Secondary shows 156.154.71.1 192.168.0.1 (no idea why it shows two, but the 2nd is the IP of my WRT54GL).
    Comcast -> SB6120 -> WRT54GL (Tomato 1.27) -> PAP2T
    Tomato settings: Ports Fowarded: 5000-65000 UDP, UDP Unreplied Timeout: 10, UDP Assured Timeout: 300, QoS Enabled, Static DHCP to PAP2T MAC address

  4. #4
    Join Date
    Jan 2009
    Posts
    230

    Default Re: possible dns issue

    ^ dnsadvantage

  5. #5
    Join Date
    Sep 2009
    Location
    New Joisey
    Posts
    301

    Default Re: possible dns issue

    Sounds like Y2K all over again (and you know how that was a big bust except lots of people made LOTS of money off everyones fear).

  6. #6
    Join Date
    Feb 2010
    Posts
    221

    Default Re: possible dns issue

    Actually, it was a lot of hard work by a lot of people that made Y2K seem to be "a bust". My wife was one of these and I know what she put in to it. The average Joe (and news pundits) had no clue.
    Steve

  7. #7
    Join Date
    Jan 2009
    Posts
    230

    Default Re: possible dns issue

    I agree with MisterEd. The bean counters listened to the hype and not their engineers. . .
    Last edited by voipinit; 05-02-2010 at 02:35 PM. Reason: deleted the rant

  8. #8
    Join Date
    Nov 2008
    Posts
    15

    Default Re: possible dns issue

    I don't see any comment from voipo yet, would like to know their path forward.
    dvijen

  9. #9
    Join Date
    Sep 2008
    Location
    Southwest MO
    Posts
    219

    Default Re: possible dns issue


  10. #10
    Join Date
    Nov 2008
    Posts
    15

    Default Re: possible dns issue

    Quote Originally Posted by scott2020 View Post
    still doesn't change the fact that as of today, dns server used by phone adapter is not ready for may 5th

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •