Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: possible dns issue

  1. #11
    Join Date
    Dec 2009
    Location
    MA
    Posts
    166

    Default Re: possible dns issue

    Can someone on the VOIPo support staff chime in?
    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

  2. #12
    Join Date
    Feb 2007
    Location
    Irvine CA
    Posts
    1,542,128,043

    Default Re: possible dns issue

    We've been told that this is essentially a non-issue by several vendors which is why you don't see it anywhere mainstream. If it were a change that could completely stop all these services, you'd be hearing about it like it was Y2K all over again.

    I'm not technical, but from what I understand, the DNSSEC responses are ONLY sent if the nameserver specifically requests them and if they are requested the users that will have issues are ones where their routers don't allow packets of that size through.

    So from what I'm being told, if a user is impacted, it'll be their entire connection...not just a VOIPo adapter but it's very unlikely.
    Last edited by VOIPoTim; 05-03-2010 at 03:23 PM.
    Timothy Dick
    Founder/CEO
    VOIPo.com

    Interact with VOIPo: Twitter, Facebook

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

    Default Re: possible dns issue

    Thanks, Dick!
    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. #14
    Join Date
    Nov 2008
    Posts
    15

    Default Re: possible dns issue

    Quote Originally Posted by VOIPoTim View Post
    We've been told that this is essentially a non-issue by several vendors which is why you don't see it anywhere mainstream. If it were a change that could completely stop all these services, you'd be hearing about it like it was Y2K all over again.

    I'm not technical, but from what I understand, the DNSSEC responses are ONLY sent if the nameserver specifically requests them and if they are requested the users that will have issues are ones where their routers don't allow packets of that size through.

    So from what I'm being told, if a user is impacted, it'll be their entire connection...not just a VOIPo adapter but it's very unlikely.
    That is not my understanding since your adapter does not use isp's dns server. 156.154.70.1 and 156.154.71.1 which adapter is using are not ready for may 5th.
    dvijen

  5. #15
    VOIPoLucas Guest

    Default Re: possible dns issue

    Quote Originally Posted by dvijen View Post
    That is not my understanding since your adapter does not use isp's dns server. 156.154.70.1 and 156.154.71.1 which adapter is using are not ready for may 5th.
    dvijen
    Dvijen,

    You might find this another useful read:

    http://www.dslreports.com/forum/r24168644-

    Also, keep in mind you're reading the register .

  6. #16
    Join Date
    Dec 2009
    Location
    MA
    Posts
    166

    Default Re: possible dns issue

    Miracle of miracles - my phone works today!
    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

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
  •