Jerome Haltom

My feedback

  1. 363 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    unplanned  ·  11 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom supported this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom shared this idea  · 
  3. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    Thank you for your suggestion on feedback.azure.com for Dynamic DNS support in Azure DNS.

    Please can you clarify a couple of points about your suggestion for us:
    1. Are you looking for Dynamic DNS support for Internet-facing domains, or for internal domains?
    2. In the case of Internet domains, how would you expect requests to be secured?

    Thanks!

    Jerome Haltom commented  · 

    I'd expect it to operate exactly like dyndns and noip and other services do. Azure DNS doesn't even have internal domains, does it?

    I wrote a Functions app to implement dyndns2, actually. If you're curious what I'm thinking of.

    https://github.com/wasabii/Cogito.AzureDynDns

    This is implements the dyndns2 protocol. Accepts BASIC authentication. Uses that to scan the configured subscription for the matching Azure DNS zone, and then updates the specified record.

    Jerome Haltom shared this idea  · 
  4. 1,014 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    50 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom commented  · 

    I'd like to add onto this: you should be able to extend the DNS secondary into a VNet. So as to export from an AD DC.

  5. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom commented  · 

    Because that's not how routing works.

    The next-hop has to actually be reachable from subnets connected to the router. You know, the next router.

  6. 73 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Azure Marketplace  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom supported this idea  · 
  7. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Active Directory » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom commented  · 

    And how would they do that, since they don't even know the login is part of your organization until AFTER you select it.

  8. 1,124 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    44 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom shared this idea  · 
  9. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom commented  · 

    Probably should not happen. This would require .NET type information to move across the wire where you probably don't want it to. The caller would have the ability to spawn instances of types on the remote service.

  10. 153 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom commented  · 

    You are free to build the Service Fabric cluster yourself, using your own ARM templates. Multiple Load Balancers are possible, as are custom VM images and everything else.

  11. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Service Fabric  ·  Flag idea as inappropriate…  ·  Admin →
    Jerome Haltom commented  · 

    You can put your Actor interface type directly on the Actor state DataContract. The framework already manages to internally convert this to an ActorReference when it needs to, and back again.

Feedback and Knowledge Base