help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

75.126.122.162 showing as an invalid IP

ANSWERED

‎03-24-2015 08:43

‎03-24-2015 08:43

Hello

 

We have configured out application to do reverse dns lookup to a fitbit domain and are stting a lot of failures from 75.126.122.162.  When I hit this in a browser, it does go to a fitbit site, however it does not seem to resolve to a fitbit domain (see below).  Is reverse dns lookup for a fitbit domain still the required approach for getting fitbit notifications?

 

 

75.126.122.162-static.reverse.softlayer.com

Best Answer
Labels:
0 Votes
1 BEST ANSWER

Accepted Solutions

‎03-24-2015 10:59 - edited ‎03-24-2015 11:04

‎03-24-2015 10:59 - edited ‎03-24-2015 11:04

@CernerWellness Apologies for this. We have corrected the configuration on that server. If you have the DNS records cached, it may take a few hours for the change to be reflected. Thank you for bringing it to our attention.

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

‎03-24-2015 08:59 - edited ‎03-24-2015 08:59

‎03-24-2015 08:59 - edited ‎03-24-2015 08:59

api.fitbit.com seems to resolve to the same SoftLayer host.

 

Maybe you should just add the softlayer host as a valid host until it's fixed, it probably won't hurt anything.

 

 

Best Answer
0 Votes

‎03-24-2015 10:59 - edited ‎03-24-2015 11:04

‎03-24-2015 10:59 - edited ‎03-24-2015 11:04

@CernerWellness Apologies for this. We have corrected the configuration on that server. If you have the DNS records cached, it may take a few hours for the change to be reflected. Thank you for bringing it to our attention.

Best Answer
0 Votes